An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. From 8th of June, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.

Hi, does anyone else have issue with App review submissions currently? My first submissions were always reviewed in under 24 hours - max I waited was 48. But the current submission has been in "waiting for review" for 2 weeks. No response from support whatsoever and phone support can't offer any help either. This is starting to get really frustrating, is this a general issue right now?

Hello, I'm hoping for advice or help from Apple staff, as my submission has been stuck for an unusually long time. Apple ID : 6757189002 Submission ID: 19cab929-810b-4a15-acfa-4b28ae84ad41 Version / Build: 1.3.0 (4) Date submitted: May 28, 2026 Current status: "Waiting for Review" for 18+ days — it has never moved to "In Review" What I've already done: We contacted Apple Support to inquire about the review status (Case ID: 102907643142); they replied that they could not specify a timeframe for the review and that no action was required on our part. Submitted an expedited review request over 72 hours ago; I have received no response and the status has not changed. Verified my account side: agreements/contracts are signed, tax and banking info is complete, and export compliance is answered. I do not see any visible issue in App Store Connect. No rejection, no "In Review", no visible error. This update is important to us: it adds iOS 15 support that users on iOS 15 devices have requested (they currently cannot use the app), and it is tied to a time-sensitive operational event. The prolonged delay is directly impacting our users and business. Could someone please check whether there is a hidden submission or account issue, or whether this is a known review queue delay? Any guidance would be greatly appreciated. Thank you.

Submitted Thursday, June 12 at 5:53pm ET. It is now Monday, June 15 at 5pm ET. Status has not moved from "Waiting for Review." No reviewer has opened the app. I'm a small indie developer — this is my second app (GoShed is live). I've been through the rejection cycle before so I know the process. The submission is clean: guest-browse architecture, Stripe for payments, PostHog analytics, reviewer credentials included, notes written specifically to preempt common flags. Apple's own page currently reads "90% of submissions reviewed in less than 24 hours." I'm at 96. I submitted a support email Sunday night and am within the 2-business-day response window. Not panicking. Just flagging for anyone else in the queue — and genuinely curious if others are seeing delays this week specifically.

Hello everyone, The App Store review process has been an absolute nightmare lately. My app has been stuck in review for way longer than it should be. No clear communication, no updates, and the support team hasn't been able to give me anything useful. The impact on my side: • Launch date completely blown. • No actionable response from Apple support. • Status page shows nothing out of the ordinary This level of opacity is genuinely unacceptable, especially for indie developers who have real deadlines to meet. Apple needs to do much better here. Anyone else dealing with this right now? Is collective feedback to Apple even worth trying at this point?

Dear App Review and Developer Support Team, Our app, CraftOS (Apple ID 6757652683), was approved and is set to release automatically, but it still cannot go live. The reason appears to be the trader status / DSA verification, which has shown "In Review" since June 8, 2026. We submitted all requested information from our individual developer account, and everything on our side appears complete and correct. Even so, the verification has not progressed for over a week, which keeps the already approved app from being released. Could you please clarify: Is there a specific reason for this extended hold on the trader / DSA verification? Is any further action or document required from our side? When can we expect the verification to be completed so the approved app can be released? We have already contacted Developer Support about this (case 102914821768), but have not received a reply in three days. Thank you very much for your time and assistance.

Our app has been stuck in “Waiting for Review” for about six full days since submission, and it has not yet entered the “In Review” stage. We would appreciate any update from the App Review team and hope the app can move into the review process as soon as possible. Apple ID: 6761810265

Hello, I would like to ask for advice regarding a long App Review delay. Apple ID: 6763960707 Our app was in the “Waiting for Review” status for more than three weeks. When the review finally started, we received an issue related to screenshots, even though the same screenshots had previously passed review without any problems. During that waiting period, we had already prepared a new app update. Since the previous build had not been approved yet, I uploaded a new build and also replaced the screenshots with updated ones that should address the reported issue. However, the app has now been waiting for review again for several more days. In total, we have been unable to release an update for almost a month. The update includes important bug fixes, improvements, and expanded functionality, so the delay is becoming a serious problem for us. I have already contacted Apple, but I have not received a response yet. Could someone from Apple please take a look at this case or advise on the proper way to escalate it? Thank you in advance.

To the Apple Review and Developer Support Teams, We are experiencing the same issue described in this thread: https://developer.apple.com/forums/thread/827016 Our application has been rejected under Guideline 2.1 - Performance because the subscription plans do not load during the App Review process. According to the review feedback, there's an error indicating that the In-App Purchases product list is empty. We are unable to reproduce this issue on our side. The subscription screen works correctly in TestFlight on multiple physical devices and with sandbox tester accounts. The paywall loads successfully, localized prices are returned correctly, and test purchases can be completed without errors. We have verified the following: All subscription products are attached to the submitted app version in App Store Connect. The product identifiers used in the application match the identifiers configured in App Store Connect. The relevant agreements, tax information, and banking details are active and up to date. The same build works correctly in TestFlight. The issue appears to occur exclusively in the App Review environment. This makes it difficult for us to diagnose the root cause or validate a fix. Could you please investigate whether there is an issue affecting StoreKit product retrieval during the review process? Any logs, diagnostics, or guidance on how to reproduce the App Review environment behavior would be helpful. Submission details: Date Submitted: Jun 1, 2026 at 2:01 PM Submission ID: 1260550e-ba11-4cbe-925a-7694f89ce715 Thank you for your assistance.

Hi everyone, I'm experiencing a frustrating situation with my app and hoping someone from Apple or the community can help or has faced the same. Situation: I configured two auto-renewable subscriptions (premium_monthly and premium_yearly) in App Store Connect under a subscription group Submitted them for review along with a new app build The app build was reviewed, accepted, and is now live on the App Store The subscriptions have been in "In Review" status for 20+ days with no action Impact: In production, StoreKit does not return the subscription products at all (as expected — Apple doesn't serve unreviewed products to StoreKit) Users cannot purchase subscriptions Monetization is completely blocked for a live, approved app What I've already tried: Submitted an expedited review request — no response Submitted a new app version update to force a combined review — app was approved again but subscriptions remain "In Review" Contacted App Store Support via the online form — no response after multiple days Cannot edit or resubmit the subscriptions because they are locked while "In Review" Technical details: Using Flutter with the official in_app_purchase package (v3.2.0) Implementation verified correct — prices load fine in sandbox/simulator Existing lifetime non-consumable (remove_ads_premium) is approved and working in production Only the two new subscriptions are stuck Questions: Is there any way to escalate a stuck subscription review beyond the standard expedited review form? Can I delete the subscriptions while they are "In Review" and recreate them, or will that cause issues with product ID reuse? Has anyone else experienced this and found a resolution? Any help or guidance from Apple engineers or fellow developers would be greatly appreciated. Thanks

Hello Apple, I am looking for guidance regarding an app that has been in review for an unusually long time. App ID: 6771651289 App Title: Authenticator App Status: In Review Review Start Date: March 23, 2026 Submission Type: First App Store Submission My app has remained in the "In Review" state since March 23, 2026, and I have not yet received any feedback, requests for additional information, or review outcome. I understand that review times can vary depending on workload and review requirements. However, the extended review period is causing a significant delay to my planned launch, and I would be grateful if the App Review Team could provide an update on the status of the review or advise whether any additional information is needed from my side. Thank you for your time and assistance. I appreciate the work of the App Review Team and look forward to your response. Kind regards, Developer of App ID 6771651289

I have finished a new app that integrates Apple hosted background asset. I have tested and confirm that the assets are downloaded both locally and with a TestFlight build. App review is not able to access the background assets. I can see that the assets are updated with status "accepted". But app review is running into error "A server with the specified hostname could not be found.". These are Apple Hosted Assets. Did I miss any configuration?

Hello, I would appreciate any insight from Apple engineers or developers who may have experienced a similar situation. Timeline: Initial submission: May 28, 2026 Status since submission: "Waiting for Review" The app has never transitioned to "In Review" Due to the extended delay, I requested an expedited review Apple approved the expedited review request More than 5 days have now passed since the expedited review approval The status remains unchanged: "Waiting for Review" Support history: I contacted Apple Developer Support multiple times regarding the review status. I eventually received the following information from Developer Support: The application is progressing through "additional internal review steps" as part of the standard evaluation process. The case was escalated to the appropriate review team for further investigation. However: No additional information has been requested from me. No Resolution Center activity has appeared. No further update has been provided. The application remains in "Waiting for Review." Case reference: case IDs (102907712466 and 102901533964 and 102915319049) This delay is having a significant impact on my planned launch and business activities, which have effectively been on hold while waiting for the review process to progress. I completely understand that some applications may require additional review, but I am trying to understand whether this situation is considered normal and whether other developers have experienced a similar timeline after: An expedited review request was approved. Apple confirmed additional internal review steps were taking place. The application still remained in "Waiting for Review" for an extended period. Has anyone encountered a similar review path, and if so, how long did it take before receiving a review decision or additional communication? Any feedback from Apple engineers or developers who have experienced this process would be greatly appreciated. Thank you.

Hi everyone, I'm looking for advice from developers who have successfully navigated Guideline 4.3(b) Spam concerns. I've been building a custom marketplace platform called Goddess Destiny Psychics. The app includes custom advisor onboarding, advisor applications, identity verification, Stripe Connect onboarding, recorded readings, live chat functionality, advisor review workflows, admin moderation tools, automated approval/rejection processes, and a custom advisor evaluation system. My first submission was rejected under 4.3(b). A later submission also included a functionality concern, which I addressed. On my most recent submission, the functionality concern was no longer present, but the app was again rejected under 4.3(b). I've submitted an appeal because I believe the app contains substantial custom functionality and differs significantly from a simple template-based app. Has anyone successfully appealed a 4.3(b) rejection for a marketplace or service-based app? If so, what information was most helpful in demonstrating that your app was sufficiently differentiated? The review was completed in a relatively short amount of time, which left me concerned that some of the app's workflows may not have been fully evaluated. Thank you for any insights.

Hi everyone, I’m having an ongoing issue where my app submissions seem to sit in Waiting for Review for unusually long periods before Apple starts reviewing them. My current submission has been stuck in Waiting for Review since June 6 at 12:56 PM. This is not the first time this has happened. I’ve had previous submissions also take much longer than expected to even move into review. I understand review times can vary, but it seems like my app is repeatedly getting delayed at the Waiting for Review stage rather than actually being reviewed. I have not received a rejection, message, metadata issue, or request for more information. The submission just stays in the queue. Has anyone else experienced repeated delays like this? Is there anything in App Store Connect that can cause an app to keep getting stuck before review starts, such as subscription review, metadata, screenshots, compliance questions, app category, or account-level issues? Would the best next step be to contact Apple Developer Support, submit an App Review inquiry, or request an expedited review? Any advice would be appreciated.

Hi guys, I’m looking for some advice regarding App Review. I submitted my first app and it was rejected. I fixed the issues and submitted a new build. That review went through in a normal amount of time, but the app was rejected again for some additional issues. I fixed everything that was mentioned and submitted another build. The problem is that this one has now been sitting in “Waiting for Review” for 9 days, which feels a lot longer than the previous reviews. Has anyone else experienced this? Should I just keep waiting, or is there something I should do at this point? I thought about requesting an expedited review, but from what I understand Apple only grants those for things like critical bug fixes, time-sensitive launches, or urgent business needs, so I don’t think my case qualifies. Any insight would be appreciated. Thanks!

I recently noticed that an app called Private Browsing Web Browser has been ranking at the top for the keyword “browser” on the App Store for a long time, even ahead of well-known browsers like Chrome, Firefox, and Safari. This is not only the case in the U.S.; it also appears to rank top in many other regions. This app has not been updated for a long time, and both its interface and feature set seem extremely basic. There also appears to be nobody to discuss it on the internet, and some of the App Store ratings look very suspicious. I previously reported this to the Apple team by email, and questioning about the algorithm, but they consistently responded: The App Store ranking system has no problem, and it's working as expected.” I wanted to ask everyone: Do you think it is normal for this app to rank number one for “browser” on the App Store? Also, the same developer has another very similar browser app called Snowbunny Private Web Browser, which also ranked high.

I deleted Build 16 from the external Test Flight review approval because I want Build 17 to be used and set up for external review. I successfully removed it and it is not showing up under external testing.. but when I try to add my Build 17, it is greyed out and says that Build 16 is still waiting for review. Can you please fix this as soon as possible so I can begin the review process for my Build 17? Please let me know what information you may need. I'm hoping to get this resolved ASAP.

Hello everyone, I'm looking for advice from developers who may have encountered a similar situation. I originally submitted an app called Bien, which provides financial services and handles sensitive user data. During review, Apple rejected the app under Guideline 5.1.1 and advised that the app must be published under a seller/company name that reflects the Bien brand. Following that guidance, we went through the process of creating a new Apple Developer account under the appropriate company identity and submitted the app again using the new account. However, the new submission has now been rejected under Guideline 4.3(a) (Spam) because the binary, metadata, and concept are similar to apps submitted under another developer account. The challenge is that the similarities exist because it is the same app, being resubmitted under the new account that Apple previously indicated should be used. We have: Submitted a formal appeal. Opened a support case with Apple. Provided the previous review communication showing the requirement to publish under the Bien company name. Has anyone experienced a situation where an app was moved to a new developer account following Apple's ownership or branding requirements and subsequently received a 4.3(a) rejection? If so: How was the issue resolved? Was additional documentation required? Did App Review eventually recognize the account transition and approve the app? Any insights would be greatly appreciated. Thank you.